![]() | ![]() | ![]() | ![]() |
On Windows Server 2003 platforms, Multi-Processing (MP) CONNECT sign-ons might fail intermittently because of the way that TCP/IP ephemeral ports are handled. The client error messages do not contain much diagnostic information. They typically show only error messages such as these:
ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: SAS did not start properly. Please ensure that your sascmd value does not attempt to run SAS in the background. ERROR: Remote signon to xxx canceled.
You might be able to find the failed SAS server session's start-up error log, which is likely to contain text such as the following:
ERROR: A communication subsystem environment initialization request failure ERROR: has occurred. ERROR: The connection was refused.
Note: These start-up error logs are commonly found under the user's Windows %USERPROFILE% folders, under a (typically hidden) application data folder tree.
On Windows versions before Vista, the path looks like this:
Whereas after Vista, the location is typically this:
The log filenames themselves are of this form: sas.1424.259335D1.log
While not definitive, these client and server error messages do help identify the problem.
The problem occurs when many SAS sessions are running at the same time, consuming TCP/IP sockets, and a new request for a socket pair has a conflict such that the server cannot bind to the ephemeral port that already is in use.
A workaround for this problem is to set the following environment variable to zero before any SAS session is started on the server:
TCP_EPH_MAP_ENABLED=0
Use the following steps to add this environment variable setting to your System Variables list so that it is set across reboots of your server:
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS/CONNECT | Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 Datacenter Edition | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 Enterprise Edition | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 Standard Edition | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 | ||
Microsoft Windows Server 2003 for x64 | 9.21_M1 | 9.3_M1 | 9.2 TS2M0 | 9.3 TS1M2 |